@aws-cdk/aws-codepipeline-api

AWS CodePipeline Actions API

This package contains the abstract API of Pipeline Actions. It's used by the aws-codepipeline module, and the AWS service modules that integrate with AWS CodePipeline.

You should never need to depend on it directly - instead, depend on aws-codepipeline, and the module you need the concrete Actions from (like aws-codecommit, aws-codebuild, etc.).

Changelog

0.12.0 (2018-10-12)

IMPORTANT NOTE: This release includes a fix for a bug that would make the toolkit unusable for multi-stack applications. In order to benefit from this fix, a globally installed CDK toolkit must also be updated:

$ npm i -g aws-cdk
$ cdk --version
0.12.0 (build ...)

Like always, you will also need to update your project's library versions:

Language | Update? --------------------------- | ------------------------------------------------------------------------------------------------------------------ JavaScript/TypeScript (npm) | npx npm-check-updates -u Java (maven) | mvn versions:use-latest-versions .NET (NuGet) | nuget update

Bug Fixes

• aws-codebuild: allow passing oauth token to GitHubEnterpriseSource (#908) (c23da91)
• toolkit: multi-stack apps cannot be synthesized or deployed (#911) (5511076), closes #868 #294 #910

Features

• aws-cloudformation: add permission management to CreateUpdate and Delete Stack CodePipeline Actions. (#880) (8b3ae43)
• aws-codepipeline: make input and output artifact names optional when creating Actions. (#845) (3d91c93)

BREAKING CHANGES TO EXPERIMENTAL FEATURES

• aws-codepipeline: this commit contains the following breaking changes:

  • Rename 'artifactName' in Action construction properties to 'outputArtifactName'
  • Rename the 'artifact' property of Actions to 'outputArtifact'
  • No longer allow adding output artifacts to Actions by instantiating the Artifact class
  • Rename Action#input/outputArtifacts properties to _input/_outputArtifacts

Previously, we always required customers to explicitly name the output artifacts the Actions used in the Pipeline, and to explicitly "wire together" the outputs of one Action as inputs to another. With this change, the CodePipeline Construct generates artifact names, if the customer didn't provide one explicitly, and tries to find the first available output artifact to use as input to a newly created Action that needs it, thus turning both the input and output artifacts from required to optional properties.